Method and program for initiating a second service in dependency of a first service

ABSTRACT

A method for initiating a second service in dependency of a first service using individually configured event-driven state-machines includes executing the first service in a first communication space; transmitting a first event to an operator unit in dependency of the first service; triggering a first event-driven state-machine of the operator unit by the first event; generating a second event by the first event-driven state-machine; transmitting the second event to at least one of the first communication space and a second communication space; and initiating the second service in the at least one of the first communication space and the second communication space by the second event.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a national stage entry under 35 U.S.C. §371of International Application No. PCT/EP2010/003539, filed Jun. 14, 2010,claims priority to European Patent Application No. EP09008206.6, filedJun. 23, 2009, and U.S. Provisional Patent Application No. 61/219,577,filed Jun. 23, 2009. The International Application was published inEnglish on Dec. 29, 2010 as WO 2010/149285.

FIELD

The present invention relates to the field of providing and executingcertain services in communication spaces.

BACKGROUND

There are a large number of different communications spaces, e.g.telephone networks, thousands of intranets, heating systems, a car, anintelligent house, millions of private computers, a model railroad, acomputer game, a net game, billions of television receivers, audio andvideo players, media servers and mobile devices, a virtual reality, theoffice suites on personal computers, a robot, the control room of aplant, a user browsing a Web page, a cruise liner, a further telephonenetwork, an airport, a satellite, a supermarket and so on. Common to allof them is, that specific information are exchanged and that within eachcommunication space the information transfer methods are optimizedaccording certain, in the main communication space specific criteria.Due to the fact that those optimization criteria differ obviously as thecase arises, each communication space is good at internal informationtransfer, but ill-suited when one thinks of external communicationoptions.

Furthermore, it is well known that there are examples where twocommunication spaces can communicate among themselves (apart fromInternet connections or similar), but those communications arewell-regulated by using well-defined interfaces with well-defined,barely extendable protocols. So e.g. a network of a mobile telephoneoperator is connected with networks of other operators in this vein. Butthese interfaces are laid out for very specific purposes in almost allcases. There is currently no universal and flexible method in orderpermit two (or more) arbitrary communication spaces to bring(supplementary) inter-workings about.

SUMMARY

In an embodiment, the present invention provides a method for initiatinga second service in dependency of a first service using individuallyconfigured event-driven state-machines, the method comprising: executingthe first service in a first communication space; transmitting a firstevent to an operator unit in dependency of the first service; triggeringa first event-driven state-machine of the operator unit by the firstevent; generating a second event by the first event-drivenstate-machine; transmitting the second event to at least one of thefirst communication space and a second communication space; andinitiating the second service in the at least one of the firstcommunication space and the second communication space by the secondevent. The first event-driven state-machine is pushed from an internetserver to the operator unit by a second event-driven state-machine. Thefirst event-driven state-machine is individually configurable by a userfor initiating the second event in dependency of the first event.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a flowchart of a method for initiating a secondservice in dependency of a first service according to a first exemplaryembodiment of the present invention,

FIG. 2 illustrates a flowchart of a method for initiating a secondservice in dependency of a first service according to a second exemplaryembodiment of the present invention.

FIG. 3 illustrates a flowchart of a method for initiating a secondservice in dependency of a first service according to a third exemplaryembodiment of the present invention.

FIG. 4 illustrates a flowchart of a method for initiating a secondservice in dependency of a first service according to a fourth exemplaryembodiment of the present invention.

FIG. 5 illustrates a flowchart of a method for initiating a secondservice in dependency of a first service according to a fifth exemplaryembodiment of the present invention.

DETAILED DESCRIPTION

In an embodiment, the present invention provides individuallyconfigurable interactions between multiple services which, in a furtherembodiment, covers multiple communication spaces in parallel and enablesthe implementation of customized and user-configured services that doesnot have the drawbacks of the prior art.

In the embodiment, a method is provided for initiating a second servicein dependency of a first service using individually configuredevent-driven state-machines comprising the steps of executing a firstservice in a first communication space, transmitting a first event to anoperator unit in dependency of the first service, triggering a firstevent-driven state-machine of the operator unit by the first event,generating a second event by the first event-driven state-machine,transmitting the second event to the first communication space and/or toa second communication space and initiating a second service in thefirst and/or in the second communication space by the second event,wherein the first event-driven state-machine is pushed from an internetserver to the operator unit by a second event-driven state-machine andwherein at least the first event-driven state-machine is individuallyconfigured by a user for initiating the second event in dependency ofthe first event.

The second service is initiated by the first event-driven state-machinewhich is indirectly triggered by the first service. Therefore, theinteraction between the first and the second service is defined by thefunctionality of the first event-driven state-machine of the operatorunit. Advantageously, the first event-driven state-machine is at leastpartly individually configurable by the user, so that the abovementioned interaction between the first and the second services can beadapted to personal requirements of the user. Beneficially, arbitraryfunctionalities between different services are feasible and freelyprogrammable by the user. In an embodiment, both the first and thesecond event-driven state-machine are individually configured by theuser. Advantageously, the user has the possibility to configure andmodify the first event-driven state-machine on the internet serverindependently from the operator unit, as the first event-drivenstate-machine is uploaded to the operator not until the firstevent-driven state-machine is requested by the operator unit with acorresponding initial event, as this corresponding initial event causesthe second event-driven state-machine to push the individuallyconfigured first event-driven state-machine to the operator unit.Therefore, the user does not need to configure the operator unitdirectly. In an embodiment, the operator unit is controlled by acommunication space operator or authority, like a mobile phone provider,which has to activate the transmission of first and/or second eventsbetween the first communication space and the internet server.

For example, the connection between a mobile network as the firstcommunication space and an internet server for initially triggering thesecond event-driven state-machine in such a manner, that the secondevent-driven state-machine pushes the customer defined firstevent-driven state-event machine to the operator unit of the mobilenetwork provider has to be activated by the mobile network provider. Ifthe mobile network provider trusts the assigned customer ID, theconnection between the mobile network and the second event-driven statemachine of the user is initiated via the operator unit, so that thesecond event-driven state-machine detects an initial event and pushesthe first event-driven state-machine towards the operator unit.Subsequently, the operator unit is capable of executing the commands ofthe first event-driven state-machine and the user is able to use hisindividually configured functionalities.

In an embodiment, the functionality and the source code of theevent-driven state-machines are checked by the mobile provider beforestoring and activating the second event-driven state-machine on theinternet server. Therefore, the mobile provider makes sure, that thesyntax of the first event-driven state-machine is correct, when thefirst event-driven state-machine is pushed towards the operator unit.

The second service is executed in the first and/or in the secondcommunication space. Thus, a connection between at least two fullydifferent communication spaces could be provided by the method in anembodiment according to the present invention where a first event or afirst service in the first communications space initiates an arbitrarysecond event or a second service in the second communication space, forinstance. In an embodiment, the initial event is forwarded to the secondevent-driven state-machine by a first application of the operator unit,wherein the first application incorporates at least partially thefunctionality and in particular even the source code of the firstevent-driven state-machine after the first event-driven state-machinehas been uploaded to the operator unit by the second event-drivenstate-machine triggered by the initial event. Subsequently, a firstcommunication between the first communication space and the operatorunit is controlled by the first event-driven state-machine which ispushed towards the operator unit and a second communication between theinternet server and the internet is controlled by the secondevent-driven state-machine on the internet server, for instance. Inparticular, the first and the second event-driven state-machinecommunicate with each other directly via a TCP/IP based interface.Advantageously, the functionality of the first event-drivenstate-machine can be adapted to arbitrary communication space. Togetherwith the individually configurable second event-driven state-machine thecustomer is able to configure arbitrary functionalities between anydifferent communication spaces. The second service could be a newservice which is independent of the second service. Alternatively, thesecond service could be a certain continuation of the first service inthe first communication space.

In an embodiment, the second communication space is linked to theinternet server via a further operator unit comprising a further firstevent-driven state-machine, wherein, in a further embodiment, thefurther event-driven state-machine is pushed to the further operatorunit by the second event-driven state-machine. It is a great advantagethat every communication path between the internet server and a certaincommunication space is individually controlled by exactly one certainevent-driven state-machine. In an embodiment, the first event-drivenstate-machine is allocated to the first communication space and thefurther first event-driven state-machine is allocated to the secondcommunication space. In an embodiment, the operator unit covers aservice provider for the first communication space, wherein the furtheroperator unit covers a further service provider for the secondcommunication space. In an embodiment, the modular principle is used, sothat the number of incorporated communication spaces and/or user-definedweb applications (and users respectively) can easily be extended byincorporating further first event-driven state-machines and/or furthercommunication spaces. Thereby, any communication space comprising aninternet connection for web-based interaction with the internet servercan be used modularly as first, further first and/or secondcommunication spaces.

In an embodiment, the first communications space is a telephone network(particularly a mobile network). Communication spaces include telephonenetworks, thousands of intranets, heating systems, a car, an intelligenthouse, millions of private computers, a model railroad, a computer game,a net game, billions of television receivers, audio and video players,media servers and mobile devices, a virtual reality, the office suiteson personal computers, a robot, the control room of a plant, a userbrowsing a Web page, a cruise liner, a further telephone network, anairport, a satellite, a supermarket and so on, for instance. A first orsecond service comprises every active or passive event in thecorresponding communication space. For example, a service could be atelephone call, a computer command, a power switch adjustment, aSOS-signal, a certain global positioning signal and so on. Furthermore,a service could be a combination of such events in one or in multiplecommunication spaces. For example, during configuration of the firstevent, the user addresses the first and the second service oralternatively the first and the second event. In an embodiment, theinternet server comprises further event-driven state-machines. In afurther embodiment, each event-driven state-machine corresponds to everycommunication space. In particular, the internet server comprises peruser at least one event-driven state-machine for at least eachcommunication space. If the internet server also comprises a setupevent-driven state-machine, the internet server features an amount of(n+1)-event-driven state machines per user, wherein the number nrepresents the total number of communication spaces that can beaddressed by for the certain user. Advantageously, the implementationand configuration of such event-driven state-machines is comparativelysimple and requires little computing power.

In an embodiment, the first communication space is linked to theoperator unit via a mediator unit, which transforms a data type of thefirst communication space into a data type applicable for the firstevent-driven state-machine and which transforms a data type of the firstevent-driven state-machine into a data type applicable for the firstcommunication space. Advantageously, the usage of such mediatorsprovides a compatible and, in an embodiment, bidirectional communicationbetween a (further) first state-event machine and the correspondingcommunication space. As a result, the method according to the embodimentcan be operated with any arbitrary communication space.

In an embodiment, the internet server transmits further events viainternet connection to further internet servers, wherein, in a furtherembodiment, the further events triggers further event-drivenstate-machines individually configured by further users. In anembodiment, the further web applications initiate further services inthe internet, in the first communication space, in the secondcommunication space and/or in further communication spaces. Forinstance, a further web event of the event-driven state-machine istransmitted to a third communication space via a further internetserver, wherein the further internet server comprises auser-configurable further first event-driven state-machine fortriggering and/or detecting further services in the third communicationspace. Advantageously, a large amount of different internet serversrepresents a parallel and therefore a comparatively fast working networkaccording to a neural network. In an embodiment, this network comprisesa large number of first and second event-driven state-machines, whereasevery first and second event-driven state machine is allocated to justone certain user and, in an embodiment, individually configured by thisuser. These different second web applications become interlinked, if thecorresponding users configure their event-driven state-machines forcorporate interaction with each other.

In an embodiment, the first, the second, the further first and/or thesetup event-driven state-machines are provided by a web page on theinternet server featuring a well-defined Uniform Resource Identifier,wherein a certain web page is allocated to a certain user and/or to acertain group of users and wherein a certain user is allocated awell-defined ID in the corresponding communication space. A “user” couldbe a software program, a single person, like a consumer or a programmer,as well as an organization, like a company or an association or thelike. Every user can be identified in a certain communication space by acertain user ID, for instance. Particularly, the first, the second andthe setup event-driven state-machines are provided by a certain web pageon the internet server for each case. In an embodiment, this web pagecontains the source code of the first, the second and the setupevent-driven state-machine, wherein the web page features a well-definedUniform Resource Identifier. The Uniform Resource Identifier is relatedto the certain user ID. The web page is also referred to ascommunication page.

In an embodiment, the first, the second, the further first and/or thesetup event-driven state-machine is configured by uploading a certainalgorithm to the internet server, by online modification of thealgorithm on the internet server and/or by clearing a certain algorithmby a provider. In an embodiment, the first, the second, the furtherfirst and/or the setup event-driven state-machine are configured by theuser with the aid of a graphical user interface and particularly thegraphical user interface comprises certain templates and/or a compilerwhich transforms graphical inputs from the user into an applicablecomputer language for the second application. Thus, an ordinary consumeris able to configure the certain event-driven state-machine for personalapplications and individual tasks in a self-explanatory and self-evidentmanner. Beneficially, a comprehensive knowledge of programming andsource-code edition is not necessary. In an embodiment, the algorithmcomprises the source code of the web page (communication page).

In another embodiment of the present invention, program is provided forinitiating a second service in dependency of a first service usingindividually configured event-driven state-machines, wherein the programcomprises at least a first and a second event-driven state-machinestored on an internet server, wherein the second event-drivenstate-machine pushes the first event-driven state-machine at leastpartially from the internet server to an operator unit, if the secondevent-driven state-machine detects an initial event from a firstcommunication space, wherein the first event-driven state-machine whichis pushed towards the operator unit controls a first communicationbetween the operator unit and the first communication space. The programfor initiating a second service in dependency of a first servicecorresponds to the method, as described above. Therefore, this programbeneficially provides individually configurable software which iscapable of partially installing itself on the operator unit, so that theuser is capable of programming personalized functionalities andinteractions between the first and the second services withoutconfiguring the operator unit directly. Furthermore, the computerprogram provides a platform for programming arbitrary and individuallyconfigurable interactions between different communication spaces.

In another embodiment of the present invention, a computer programproduct and/or a computer network is provided that comprises a programfor initiating a second service in dependency of a first service asmentioned above.

These and other characteristics, features and advantages of the presentinvention will become apparent from the following detailed description,taken in conjunction with the accompanying drawing, which illustrate, byway of example, the principles of various exemplary embodiments of theinvention. The description is given for the sake of example only,without limiting the scope of the invention. The reference figuresquoted below refer to the attached drawing.

The present invention will be described with respect to particularexemplary embodiments and with reference to a certain drawing but theinvention is not limited thereto. The invention is limited only by theclaims. The drawings are merely exemplary and are non-limiting. In thedrawing, the size of some of the elements may be exaggerated and notdrawn to scale for illustrative purposes.

FIG. 1 shows a flowchart 1 of a method for initiating a second servicein dependency of a first service according to a first exemplaryembodiment of the present invention. The flowchart 1 comprises a firstcommunication space 2, a mediator unit 3, an operator unit 4, aninternet server 5 and a second communication space 6. The firstcommunication space 2 features a core network 2′ of a mobilecommunications network, wherein the second communication space 6 coversthe World Wide Web 6.

A first service 10 in the first communication space 2 is transmitted tothe mediator unit 3 with an operator interface 30. The operatorinterface 30 serves for the core network control purposes. The mediatorunit 3 belongs to the first communication space 2 and translatescommands and data in the command language of the core network 2′ intocommands and data applicable for the operator unit 4 and vice versa. Theoperator unit 4 comprises a first application 4′ which handles firstevents 11 from the mediator unit 3. Furthermore, the first application4′ communicates with a second event-driven state-machine 15 on theinternet server 5 via an Operator-server-interface 32, preferably aTCP/IP based interface. The internet server 5 is connected to a secondcommunication space 6 and capable of initiating second services 13 inthe second communication space 6, like transferring data with furtherinternet servers, modifying web based data bases or the like. Thisinterface is called Internet-interface 33. In an optional embodiment ofthe present invention a further operator unit is provided between theinternet server 5 and the second communication space 6. This furtheroperator unit can be included (e.g. as an application programminginterface API) into the second event-driven state machine 15 on theinternet server 5, for instance.

The second event-driven state-machine 15 is individually configurable bya certain user. An admission for the internet server 5, as well as theconnection between the internet server 5 and the operator unit 4 has tobe activated for the certain user by the mobile provider. Afterwards,the user can upload an individual configured web page to the internetserver 5 comprising a first event-driven state-machine 14, the secondevent-driven state-machine 15 and a setup event-driven state-machine 16.In an embodiment, the syntax of the web page is checked by the mobileprovider during uploading to the internet server 5, so that the secondweb page is only accepted and activated when the first, the second andthe setup event-driven state-machines 14, 15, 16 are error-free. The webpage is also referred to as communication page 5′ (ComPg), which isstored on the internet server 5 available via a well-defined URI. Thefirst event-driven state-machine 14 is called “ComPg_Tel” and isdesigned to handle a first communication 14′ between the core network 2′and the second event-driven state-machine 15, wherein the secondevent-driven state-machine 15 is called “ComPg_Web” and is designed tohandle a second communication 15′ between the first event-drivenstate-machine 14 and the World Wide Web 6. The setup event-drivenstate-machine 16 includes personal information about the user. If aninitial first service 10′ in the core network 2′ is assigned to thecertain user, the operator unit 4 sends a corresponding initial event 11called “INITIAL” to the internet server 5. The event “INITIAL” triggersthe second event-driven state-machine 15 “ComPg_Web” in such a manner,that the first event-driven state-machine 14 “ComPg_Tel” is pushedtowards the operator unit 4. Subsequently, the operator unit 4 iscapable of operating first services in accordance with theuser-configured first event-driven state-machine 14 “ComPg_Tel”.Particularly, the processing of the first events 11 by the operator unit4 is determined by the first event-driven state-machine 14. The internetserver 5 operates furthermore in accordance with the second event-drivenstate-machine 15 “ComPg_Web”, wherein the second event-drivenstate-machine 15 defines the processing of events from the firstevent-driven state-machine 14 via the Operator-server-interface 32, aswell as second services 13 in the World Wide Web 6.

The proposed method in an embodiment enables telephony users to managetheir communications by means of processing commandments depositedwithin the Web. Those processing commandments may lie alongside of otheruser Web contents (e.g. Web pages or arbitrary user files) and have tobe hosted by an Internet service provider (ISP) 5 correlated with theuser's telephony operator unit 4 in such a way that a particularbipartisan mutual trust exists. Due to the facts that such commandmentsgovern arbitrary user communications in consideration of her telephonybehavior and that the commandments are located within the Web 6, theyare called communication pages 5′.

There is at most one communication page 5′ per public useridentification assigned to the user as e.g. a telephone number. Thosepages are called direct communication pages (Direct ComPg). A directcommunication page can be addressed by means of an URI derivable fromthe served user's identity (e.g., via an address such ashttp://www.ComPg.T-Mobile.org/ComPg/+49-171-6289xxx/CnmPg.bxt). It isfurther possible to combine multiple public identities on one dedicatedcommunication page (Indirect communication pages, Indirect ComPg) byreferencing the related URI from the direct communication pages assignedto the IDs involved. There is in principal no restriction with respectto the amount of direct communication pages referring to an indirectcommunication page. It is further possible that indirect communicationpages refer to another indirect communication page. A communication page5′ may be of a direct and an indirect nature at the same time.

Communication pages 5′ are built at least partly by the user. This couldbe done by completing prefabricated provisional communication pages 5′(simply by assigning values to variables, e.g. the own telephonenumber), by using a user friendly tool (comparable with the populartools to compile an “ordinary” web page) or by instantaneous editing ofthe page content. Communication pages 5′ have to be uploaded to the ISPserver 5 subsequently. The Internet Service Provider 5 should not acceptan erroneous communication page 5′ or a communication page 5′ which isgoing to address (telephony) capabilities not granted for the pageowner. The technical system under control of those pages presupposesthat all communication pages 5′ available on a server of trusted ISP 5are free from defects and are in line with the possibilities permittedto the served user.

The content of communication pages 5′ can be seen as a description of arather simple event-driven state-machine 14, 15, 16. Any external eventmay trigger an action or a concatenation of actions and may cause astate change in addition. Dependent on the state entered, one and thesame event might be treated differently. Actions can be shaped forarbitrary purposes, e.g. in order to generate another event (e.g., toinstruct a telephony system for certain activities), to call a piece ofsoftware running at the Internet Service Provider side or locatedanywhere within the Internet or on the user's PC (as e.g. generating anE-Mail to a certain addressee (or multiple addressees) providing acertain content) or to set or modify one or multiple communication pagesvariables. In addition an action could interrogate variable values andcould combine terms by arbitrary logical operations in order to come toa decision.

Beside the provisioning of variables with values provided along withevents, others variables might be accommodated with static valueswell-declared within the communication page 5′ (e.g. public telephonenumbers, URI's of E-Mail accounts, of utilizable software or of anyother Web content, passwords or entire data structures (as e.g. a listof all contacts maintained by the user)). A next type of variables inturn will be filled on per transaction basis, as e.g. the actual dateand time as well the identity of the current communication partner.

Aside from the declarations (also referred to as setup event-drivenstate-machine 16, see above), communication pages 5′ include at leastfirst and second event-driven state-machines 14, 15 generally: In thepresent example, the first event-driven state-machine 14 is relevant forserving telephony system (e.g. the mobile network 2′) and the secondevent-driven state-machine 15 “ComPg_Web” cares about Web interactionsWhereas the Web part got the responsibility for supervision andprocessing of events originated from the surrounding Internet, thetelephony part is downloaded to the application layer of the servingtelephone network operator unit 4 (when necessary) and controls therethe entire telephone communications of the user meant.

A communication page 5′ once accepted by the Internet Service Provider 5causes two things in principle:

First the Internet Service Provider starts dedicated software whichforms a Web related, user specific second application 5′ by interpretingthe second event-driven state-machine 15 “ComPg_Web” of thecommunication page 5′ (Initiating machine state is W_NULL). The secondevent-driven state-machine 15 is responsive to “Web events” which areevents either from anywhere out the Web space or from the servingtelephone network. A Web event is just attended by the machine whenspecified on the second event-driven state-machine 15 of thecommunication page 5′ (operator or user defined). If so, one or multipleactions are executed and even one (or multiple) outgoing events might begenerated due to this.

Each user is permitted to define as many Web events (and correspondingactions) as necessary for her purposes. Beyond it is up to theevent-driven state-machine 14, 15 how an external contact attempt (firstevent 11) (from outside) is mapped to a second event 12 andwhether/which/how parameters are passed thereby. There are many fittingapproaches to do so. The given document assumes a specific Webapplication programming interface (API) whereby each Web event (as faras defined for a communication page 5′) got a unique (tag-) value(WebEvent=<name>) to be used whenever a certain event (<name>) shall beaddressed via the Web application programming interface.

There are two (operator) pre-defined Web events (those which are addedautomatically to the communication page 5′ right before storing the pageand which cannot be manipulated by the user: a web event which is called“TELEPHONE”-event and a web event which is called “ONHOOK”-event, forinstance.

The web-event “TELEPHONE” (WebEvent=TELEPHONE) is addressed by thetelephone network (first communication space 2) whenever a request for atelephone transaction has been encountered for the served user. Moreoverthis event is linked constantly with following actions:

Action1: Check whether the maximum number of allowed paralleltransactions (‘MAXNumberOfParallelTransactions’) is already reached. Ifso, refuse the request. Continue with next action otherwise. Action2:Assign a unique number to the new transaction. Action3: Update thestructure ‘CURRENTTransactions’. This structure maintains a transactionnature per transaction currently processed for a certain user (e.g. SOC(subscriber originated call), STC (subscriber terminated call. WIC (Webinitiated call), MSO (message originated), MST (message terminated), SOU(subscriber originated USSD dialogue), WOU (Web originated USSDdialogue), etc.).The structure lists transactions in the order of theirinvocations. So the last listed transaction is the one the telephonenetwork is actually asking for. Action4: Push the first event-drivenstate-machine 14 “ComPg_Tel” of the communication page 5′ towards thetelephone network (This includes the provisioning of the actualstructure ‘CURRENTTransactions’.).

The web event “ONHOOK” (WebEvent=ONHOOK) is addressed by the telephonenetwork (first communication space 2) whenever a telephone transactionhas been completed. Also this event is linked constantly with an action:Update the structure ‘CURRENTTransactions’ by withdrawal the linerelated to the transaction terminated.

Second as soon as the first event-driven state-machine 14 “ComPg_Tel” ofthe communication page 5′ has been obtained from the internet server 5,the network of the serving telephone operator 4 (also called operatorunit 4) takes care about the telephony processing commandments made bythe user. For this purpose a dedicated application is running within theoperator domain. This application might act as a classic IN service ontop of a circuit switched based telephone network 2′ or even as a nextgeneration network (NGN) application server. Common to both is theability to control in principle arbitrary telephony transactions. Theamount of control options available for such an application dependsprimarily on relating methods implemented within the subjacent andoperator specific telephone network.

The first event-driven state-machine 14 of the communication page 5′forms partly a telephony related event-driven state-machine of the firstapplication and is responsive to telephony events 11 (TELEvents) whichare events either from the telephone network 2′ under control or fromthe serving Internet Service Provider (Initiating machine state isT_NULL). At the beginning the application has the ability to process areduced set of (operator) pre-defined TELEvents 11 only. Not until thefirst event-driven state-machine 14 of the communication page 5′ hasbeen received, the processing capabilities of the application areexpanded by user specific TELEvents 11 and relating actions.

A TELEvent 11 is just attended by the first application when eitherpre-defined or specified by the user in the first event-drivenstate-machine 14 “ComPg_Tel”. If so, one or multiple actions areexecuted and even one (or multiple) outgoing events 12 might begenerated due to this. Outgoing events 12 which are directed towards thetelephone network are translated to core network 2′ instructionsappropriate to the operator capabilities and methods implemented withrespect to the control interface.

As far as events from the serving Internet Service Provider areconcerned, each user is permitted to define as many TELEvents 11 (andcorresponding actions) as necessary for her purposes. Beyond it is up tothe state-event machine how a contact attempt from the Internet ServiceProvider 5 is mapped to a TELEvent 11 of the ComPg_Tel 14 andwhether/which/how parameters are passed thereby. Each TELEvent 11 (asfar as defined for a communication page) got a unique (tag-) value (e.g.TELEvent=<name>) to be used whenever a certain event shall be addressedfrom either direction.

There are a number of (operator) pre-defined TELEvents (those which areeither known implicitly by the telephone operator application (firstapplication 4′) or which are added automatically to the communicationpage 5′ right before storing the page; pre-defined TELEvents cannot bemanipulated by the user; nevertheless it might be necessary that theuser has to define one (or multiple) actions for certain pre-definedevents).

In an embodiment, one pre-defined TELEvent exists for the direction fromthe Internet Service Provider 5. From the telephone network 2′ two ofthose TELEvents are envisaged.

The first TELEvent: PUSHComPg is addressed by the Internet ServiceProvider 5 whenever the second event-driven state-machine 15 has beenrequested to push the first event-driven state-machine 14 of thecommunication part 5′ (and additional information as e.g. the structureCURRENTransactions) towards the telephone network 2′ to the operatorunit 4. The activator for this request could reside anywhere within theInternet 6 or could be even the telephone network 2′ itself. A useraction should be defined mandatory for the given event so that followingactions are performed:

Action 1: Store the first event-driven state-machine 14 ComPg_TEL of thecommunication page 5′ as well as all provided additional information(The ComPg_Tel enhances the first application 4′ of the operator unit 4for the duration of the upcoming transaction with user events andactions.). Action 2: Execution of user action(s): All details for thedesired transaction should have been determined by the user withinComPg_Tel 14. These details are converted by the application to operatorspecific core network (CN) instructions, dependent on the general CNcontrol interface available. The following options exist roughly for theuser: a) INITIATETransaction: Initiate a transaction in order to causethe system to initiate a call or an USSD (Unstructured SupplementaryService Data) dialogue. b) CONTINUETransaction: Continue a transactionin order to cause the system to develop an existing transaction (call,message or USSD dialogue) anyhow further (e.g. to setup a call to acertain (or multiple) destinations or to answer an USSD request from amobile subscriber). c) RELEASETransaction: Release a transaction inorder to eliminate a call party from a transaction or to end the entiretransaction respectively. d) PROMPTTransaction: Prompt a transaction inorder to prompt a call party for some input. For all these options theuser could name additionally transaction progress types to be supervisedby the telephone network 2 (compare to TelEvent=REPORT further down).The options have to be seen in connection with the nature of theactually given transaction. Moreover there is a good deal of involvedcontrol variable as e.g. destination numbers, the number to be presentedat destination or identities of transaction Iegs meant. Finally it is upto the telephone operator to publish the exact syntax on allpossibilities granted in this context. The present document just intendsto give an approximate idea on those user capabilities. Action 3: Changestate from the initiating machine state (T_NULL) to the machine state“started” (T_STARTED).

The first state-event machine 14 (embedded in the first web application4′) is even enabled to generate parallel TELEvents. Each of theseTELEvents causes a separate telephone application instance workingindependently from other instances created. Based on this there is e.g.the possibility to initiate multiple calls sharing the same conferenceroom (located anywhere, but reachable for the telephone operator unit4).

The second TelEvent INITIAL is addressed by the telephone network 2′whenever a request for a telephone transaction has been encountered forthe served user. Moreover this event is linked constantly with followingaction: Send the Web event 12 WebEvent=TELEPHONE to the secondevent-driven state-machine 15 on the internet server 5. This eventincludes information about the nature of transaction encountered (e.g. acall or message from/to a served user or a subscriber originated USSDdialogue). After this the application is awaiting the TELEventTelEvent=PUSHComPg from the ISP.

A third TelEvent REPORT is addressed by the telephone network 2′whenever a progress has been recognized for the maintained transaction.Such a progress could be of arbitrary nature, as e.g. transaction setupfailure or success, trigger in the middle (of transaction), transactionreleased (any party) or the arrival of some input from a party involved.The progress types to be attended for a transaction result from acombination of types to be supervised by default (operator specific)with types to be armed with respect to the user's first event-drivenstate-machine 14 (ComPg_Tel) received by means of the first TELEventPUSHComPg. Default progress types are (e.g.) ‘transaction setup failure’and ‘transaction released’. This event might or might not be linked witha user action as follows (only the progress type examples named rightbefore are taken into account; there could be types in addition) (linenumbers in brackets):

CASE (PROGRESSType) (1)  OF FAILURE: (2)     IF (USERAction forPROGRESSType defined?) (3)     THEN (4)       Execution of useraction(s); (5)     ELSE (6)       Send WebEvent=ONHOOK; (7)      Instruct the telephone network to continue (8)       (transactionrelease); (9)       Change state (from ‘T_STARTED’) to ‘T_NULL’; (10)    Fl (11)   OF SUCCESS: (12)     Execution of user action(s) forPROGRESSType; (13)   OF MIDDLE: (14)     Execution of user action(s) forPROGRESSType; (15)   OF RELEASED: (16)     IF (USERAction forPROGRESSType defined ?) (17)     THEN (18)       Execution of useraction(s); (19)     ELSE (20)       Send WebEvent=ONHOOK; (21)      Instruct the telephone network to continue (22)       (transactionrelease); (23)       Change state (from ‘T_STARTED’) to ‘T_NULL; (24)    Fl (25)   OF INPUT: (26)     Execution of user action(s) forPROGRESSType; (27) CASE END (28)

The event types ‘SUCCESS’, ‘MIDDLE’ and ‘INPUT’ will be armed only, whencorresponding user action(s) are defined within the first event-drivenstate machine 14 (ComPg_Tel).

Other important events: The event type ‘INITIATE’ is sent out in orderto cause the core network 2′ to initiate a call or an USSD dialogue. Theevent type ‘CONTINUE’ is sent out in order to cause the core network 2′to develop the maintained transaction (call, message or USSD dialogue)anyhow further (e.g. to setup a call to a certain (modified or multiple)destinations or to answer an USSD request from a mobile subscriber). Itis even possible to trigger the core network 2′ for a transactioncontinuation without modifying any transaction parameter (classiccontinue). Furthermore, the event type ‘RELEASE’ is used to eliminate acall party from a transaction or to end the entire transactionrespectively. The event ‘PROMPT’ is sent out in order to cause the corenetwork to prompt a call party for some input and/or to play anannouncement(s).

The entire mechanism enables to realize amazing, so far unknown featuresaround a real telephone network 2′. The possibilities offered go farbeyond of a rather unspectacular Internet controlled telephony net. Infact it has it in oneself to add really new services to the today's andfuture telephony world. More, the present technology allows combiningtelephone networks 2′ and Internet 6—right now (saving invests) andfuture-proof (without impacts on (perhaps) already compiled migrationstrategies towards a NG network architecture). Telephone technologiesand the method according to the present invention coalesce.

Furthermore, services go individual. As soon as a user is permitted tosee for her web application respectively her Communication Page 5′, sheis able to create her own and personalized services. It is furtherpossible to merge users with joint interests to constitute communitiesand to define communication rules appropriate to their needs. BecauseCommunication Pages 5′ form another user content, the involved operatingcompanies will take care to protect those pages against unauthorizedaccess attempts.

Telephone operator unit 4 and ISP 5 are enabled to utilize the mechanismto implement new services for the mass-market. An operator/ISP 4, 5capable of processing the method described above will have an edge overcompetitors which fail to do so. Furthermore, the mechanism describedabove offers another technical method for quite a number of knownservices.

These days it is rather uninspiring when a telephone network service 11obtains its data from the Internet 6 and acts according these data. Thesame is true for Web services 13. But an exciting innovation is anInternet content covering both, where a network of a real telephoneoperator unit 2 and the Web 6 are enabled to control them in parallel,concerted by events and shaped according individual needs. Usingembodiments of the present invention, it is no longer solely up to atelephone operator how her users are served. In fact each single userwill be permitted to adjust his personal service to a great extent.Furthermore, he need not to purchase a telephone network 2′ for thispurpose, because it becomes possible as soon as her operator iscompliant with the above mentioned technology.

FIG. 2 shows a flow chart of a method 1 for initiating a second servicein dependency of a first service according to a second exemplaryembodiment of the present invention. The first web application 4′ andthe communication pages 5′, 103 of different users are hosted by atelephone operator unit certified Internet Service Provider 5. As soonas a certain Communication Page 5′ is uploaded to an ISP server 5, arelated second event-driven state-machine 15 ComPg_Web of theCommunication page 5′ (re-) starts at ISP 5 side. In general, theinternet server 5 comprises multiple communication pages 5′, 103,wherein exact one communication page 5′, 103 is allocated to a certainuser. One of these communication pages 5′, 103 is activated by theoperator unit 4. This communication page 5′ comprises multiplestate-event machines 15, 15′, at least one event-driven state-machine14, 15 per communication space 2, 6. The first event drivenstate-machine 14 which is related to the first communication space 2 (amobile network 2′) is pushed towards the operator unit 4 by theactivated second event-driven state-machine 15. Consequently, a firstapplication 4′ running on the operator unit 4 incorporates at leastpartly the first event-driven state-machine 14 ComPg_TeI of thecommunication page 5′ and got the responsibility to handle the actualdesired (telephone) transaction for the served user. The operator unit 4is connected via a mediator unit 3 to a mobile network 2′ with anoriginating part 100 and a terminating part 101. The first event-drivenstate-machine 14 consists of an operator pre-defined part and anotherpart which interprets (the user specific) commands of the firstevent-driven state-machine 14 (ComPg_Tel). Immediately after machinestarts the actions envisaged for the operator pre-defined eventTelEvent=PUSHComPg are executed. In this context there should be atleast one action given by the user within the first event-drivenstate-machine 14 (ComPg_Tel) to be processed right now. Mainly this useraction determines the instruction to be posted subsequently towards theCN 2′ under control. As an option there could be a mediating application(mediator unit 3) in between of the operator's state-machine 4 and thecore network 2′ (CN). This mediator 3 is operator specific and acts asordinary IN node or NGN application server from CN 2′ point of view. Thefirst web application 4′ (first event-driven state-machine 14) has theresponsibility to care about user transactions, independently onpossible other, parallel transactions of the same user. The secondevent-driven state-machine 15 on the ISP 5 is in charge of combininguser transactions (same or different user(s)).

FIG. 3 shows a flow chart of a method for transmission data according toa third exemplary embodiment the present invention, the third exemplaryembodiment is similar to the first exemplary embodiment illustrated inFIG. 1 and shows a dedicated example of a communications page 5′ and thecorresponding call flows. The example describes a call flow between twousers, Alice and Bob. The single steps of the call flow are illustratedin a chronological order relating to the vertical direction. The userAlice organized her communication page 5′ on the internet server 5 insuch a manner that she can reach Bob by dialing a private number (e.g.200) instead of his official public telephone number (e.g.+49-171-6269xxx). Moreover, Alice and Bob aligned their services withrespect to a private numbering scheme so that the caller's number(Alice, +49-160-1212xxx) is presented on Bob's terminal in accordancewith the private numbering (e.g. 100) scheme. In addition, Alice added asimple screening function to her communication page 5′ (experiential sheacquired the habit to compare her telephone bill with the screening listonce a month). So her service maintains a simple Internet text file“MYFILE” (located on her Web share) containing relevant data of alltelephone calls (and call attempts) made.

The communication page 5′ of Alice is available on the internet server 5and comprises the first event-driven state-machine 14, the secondevent-driven state-machine 15 and a setup event-driven state-machine 16.

The setup event-driven state-machine 16 (also referred to as“DECLARATIONS”) discloses the personal information about Alice, like hername, a file with a digital photo of her, her public telephone numberher permissions concerning the mobile network provider. Furthermore, aprivate numbering scheme of the users Alice, Bob and Ed is defined,whereby the private number 100 and the nick name “CHERUBAlice” areallocated to the public telephone number “+49-160-1212xxx”, the privatenumber 200 and the nick name “BOBTheBuck” are allocated to the publictelephone number “+49-171-6269xxx” and finally the private number 999and the nick name “Ed” are allocated to the public telephone number“+49-228-936-33xxx”. The source code of the setup event-drivenstate-machine 16 is provided below (line numbers in brackets):

    <ComPg> (1)  <DECLARATIONS> (2)  <SERVEDUser>+49-160-1212xxx</SERVEDUser> (3)   <CUSTOMERName>Fish,Alice</CUSTOMERName> (4)   <WEB2.TPermission>basic</WEB2.TPermission>(5)   <MYPICTURE> (6)  http://www.ComPg.T-Mobile.org/ComPg/+49-160-1212xxx/me.jpg”   (7)  </MYPICTURE> (8)   <MYFILE> (9)  http://www.ComPg.T-Mobile.org/ComPg/+49-160-   1212xxx/screening.txt”(10)   </MYFILE> (11)   <MYPRIVATEScheme> (12)    <Contactname=“CHERUBAlice”> (13)      <PUBLIC>+49-160-1212xxx</PUBLIC> (14)     <PRIVATE>100</PRIVATE> (15)    </Contact> (16)    <Contactname=“BOBThebuck”> (17)      <PUBLIC>+49-171-6269xxx</PUBLIC> (18)     <PRIVATE>200</PRIVATE> (19)    </Contact> (20)    <Contactname=“Ed”> (21)      <PUBLIC>+49-228-936-33xxx</PUBLIC> (22)     <PRIVATE>999</PRIVATE> (23)    </Contact> (24)   <MYPRIVATEScheme>(25) </DECLARATIONS> (26)

The second event-driven state-machine 15 is triggered by WEBEventsreceived from the outer World Wide Web 6 or from the operator unit 4. Afirst section <TELEPHONE> of the second event-driven state-machine 15relates to telephony WEBEvent and pushes the first event-drivenstate-machine 14 to the operator unit 4 and changes the current numberof transactions. A second section <ONHOOK> relates to another telephonyWEBEvent which is received when the telephone connection is disconnectedand which triggers again a change of the current transaction number.Each of the subsequent sections <U_SCREEN2>, <U_SCREEN456>, <U_SCREEN7>and <U_SCREEN9> concern to WEBEvents for writing the actual connectionstatus of Alice's telephone extension into a web file “MYFILE” (tocompare her telephone bill with the screening list once a month). Thesource code of the second event-driven state-machine 15 is providedbelow (line numbers in brackets):

   <ComPg_Web) (1) <WEBEvents> (2)  <TELEPHONE> (3)   <ACTIONList> (4)   <ACTION>query CURRENTTransactions of    SERVEDUser</ACTION> (5)   <ACTION> (6)    assign a new TRANSACTIONNumber and update (7)   CURRENTTransactions (8)    </ACTION> (9)    <ACTION> (10)    sendPUSHComPg incl. CURRENTTransactions (11)    </ACTION> (12)  </ACTIONList> (13)  </TELEPHONE> (14)  <ONHOOK> (15)   <ACTIONList>(16)    <ACTION>update CURRENTTransactions</ACTION> (17)   </ACTIONList>(18)   </ONHOOK> (19)  <U SCREEN2> (20)   <ACTIONList> (21)   <ACTION>send SCREEN2 towards MYFILE</ACTION> (22)   </ACTIONList>(23)   </U SCREEN2> (24)   <U SCREEN456> (25)    <ACTIONList> (26)    <ACTION>send SCREEN456 towards     MYFILE</ACTION> (27)   </ACTIONList> (28)   </U SCREEN456> (29)   <U SCREEN7> (30)   <ACTIONList> (31)     <ACTION>send SCREEN7 towards MYFILE</ACTION>(32)    </ACTIONList> (33)   </U SCREEN7> (34)   <U SCREEN9> (35)   <ACTIONList> (36)     <ACTION>send SCREEN9 towards MYFILE</ACTION>(37)    </ACTIONList> (38)   </U SCREEN9> (39)  </WEBEvents> (40)</ComPg Web> (41)

The first event-driven state-machine 14 is pushed towards the operatorunit 4 by the second event-driven state-machine 15. The firstevent-driven state-machine 14 is triggered by TELEvents received fromthe mobile network 2 and from the mediator unit 3 respectively. Thefirst TELEvent is PUSHComPg for extending the first application 4′according to the first event-driven state-machine 14 and storing thecurrent transaction numbers. Furthermore, the private numbering schemeof Alice is activated and the requested private or public numbers aresent to the mobile network 2. Furthermore, the first event-drivenstate-machine 14 comprises the sections INITIAL, REPORT, SUCCESS andRELEASED for Initiating the WEBEvents <TELEPHONE>, <U_SCREEN456>,<ONHOOK>, <U_SCREEN7>, <U_SCREEN2> and <U_SCREEN9> in the secondevent-driven state-machine 15, as described above. The source code ofthe first event-driven state-machine 14 is provided below (line numbersin brackets):

   <ComPg Tel> (1) <TELEvents> (2)  <PUSHComPg> (3)   <ACTIONList> (4)   <ACTION> (5)    extend SEM according ComPg_Tel received and store (6)   CURRENTTransactions (7)    </ACTION> (8)    <USERACTIONList> (9)    CASE (CURRENTTransactions.LAST) (10)     OF SOC: (11)      <ACTION>(12)      calculate DESTNumber by mapping a called PRIVATE to      (13)     PUBLIC number (14)      </ACTION> (15)      <ACTION> (16)      forcalls to Bob set CLIPNumber to my PRIVATE one (17)      </ACTION> (18)     <ACTION> (19)      arm progress types FAILURE, SUCCESS and RELEASED     (20)      </ACTION> (21)      <ACTION>send CONTINUE (22)     </ACTION> (23)      <ACTION> (24)      send U SCREEN2 withDESTNumber, called PRIVATE      number (25) and CURTimestamp (26)     </ACTION> (27)     OF ELSE: (28)      <ACTION> (29)      armprogress types FAILURE and RELEASED (30)      </ACTION> (31)      <ACTION>send CONTINUE</ACTION> (32)     CASE END (33)   </USERACTIONList> </ACTIONList> (34)   </PUSHComPg> (35)   <INITIAL>(36)     <ACTIONList> (37)      <ACTION> (38)      send TELEPHONE withall parameters received (39)      </ACTION> (40)     </ACTIONList> (41)  </INITIAL> (42)   <REPORT> (43)     <ACTIONList> (44)      CASE(PROGRESSTYPE) (45)      OF FAILURE: (46)       <USERACTIONList> (47)       <ACTION>send CONTINUE</ACTION> (48)        <ACTION> (49)       send U SCREEN456 with CURTimestamp (50)        </ACTION> (51)      </USERACTIONList> (52)       <ACTION>send ONHOOK</ACTION> (53)     OF SUCCESS: (54)       <USERACTIONList> (55)        <ACTION>sendCONTINUE</ACTION> (56)        <ACTION> (57)        send U SCREEN7 withCURTimestamp (58)        </ACTION> (59)       </USERACTIONList> (60)     OF RELEASED: (61)       <USERACTIONList> (62)        <ACTION>sendCONTINUE</ACTION> (63)        <ACTION> (64)        send U SCREEN9 withCURTimestamp (65)        </ACTION> </USERACTIONList> (66)      <ACTION>send ONHOOK</ACTION> (67)      OF ELSE: (68)      <ACTION>send CONTINUE</ACTION> (69)      CASE END (70)    </ACTIONList> (71)    </REPORT> (72)   </TELEvents> (73)  </ComPgTel> (74) </ComPg> (75)

In a first step 40 Alice dials the private number 200 of Bob. Thisrequest (containing the private number) is transmitted from the corenetwork 2′ (first communication space 2) to the mediator unit 3. In asecond step 41 the mediator unit 3 transforms the request into a commandapplicable for the operator unit 4 which features the calling partyaddress of the serving user (Alice). The operator unit 4 addresses therequest to the corresponding communication page 5′ of the served user ina third step 42 as the first web event 11. It is however required thatthe served user is registered and trusted by the mobile networkprovider. Furthermore, the communication page 5′ of the user has alreadyto be uploaded to the internet server 5. The first web application 5′comprises the above mentioned communication page 5′ (ComPg), wherein theuser-ID (lines 3, 4 SEM 16 (event-driven state-machine 16)) of theserved user and the requested numbering scheme (lines 12 to 25 of SEM16) are defined in the setup event-driven state-machine 16. The firstevent 11 is processed in the second event-driven state-machine 15 of thecommunication page 5′ and the corresponding actions (cp. lines 3 to 14of SEM 15) for this <TELEPHONE> event are processed by the second webapplication 5′. Thus, in a fourth step 43 the first event-drivenstate-machine 14 of the communication page 5′ is pushed to the operatorunit 4 (cp. line 11 of SEM 15). Furthermore, the current transactionnumber is updated (line 7 of SEM 15) to check whether a maximum numberof permitted parallel transactions is already achieved. Subsequently,the “PUSHComPg”-section of the first event-driven state-machine 14 ispushed to the operator unit 4 and integrated into the first webapplication 4′. The official telephone number of Bob which correspondsto the private number 200 is derived from the setup event-drivenstate-machine 16 and sent together with the private number of Alice(command “CONTINUE) via the mediator unit 3 to the core network in fifthand sixth steps 44, 45 (lines 12 to 27 of SEM 14). The core network 2′develops the maintained transaction call using the public telephonenumber of Bob +49-717-6269xxx, wherein Alice's private number 100 ispresented at Bob's display. In a subsequent seventh step 46 a timestamp,as well as the private and the public called telephone numbers aretransmitted as the second event 12 to the second event-drivenstate-machine 15 as a WEBEvent called SCREEN2 (line 25 of SEM 14).Because of this WEBEvent the section <SCREEN2> of the secondevent-driven state-machine 15 is activated and the timestamp is sent asthe second service 13 to a certain Web file “MYFILE” in the World WideWeb 6 (line 22 of SEM 15) in an eighth step 47. The World Wide Web 6 hasto been seen as the second communication space 6. Subsequently, the corenetwork 2′ routes the telephone extensions of Alice and Bob in a furtherstep 48 to enable a telephone link 54. In ninth and tenth steps 49, 50the core network 2′ informs the operator unit 4 via the mediator unit 3that the telephone link 54 between Alice and Bob has been establishedsuccessfully. As instructed in the first event-driven state-machine 14of the communication page 5′ (lines 56 and 58 of SEM 14) the operatorunit 4 sends a “CONTINUE”-command to the mediator unit 3 in a eleventhstep 51 and a “U_SCREEN9”-command to the internet server 5 in a twelfthstep 52. The second event-driven state-machine 15 detects the“U-SCREEN7”-command (cp. line 30 of SEM 15) and sends a SCREEN7-stringtowards the Web file called “MYFILE” in the Web 6 in the course of athirteenth step 53 (cp. line 32 of SEM 15). Now, a conversation via thetelephone link 54 between Alice and Bob in a common way is provided(enabling the telephone link 54 could also be seen as the second service13 which continues the first service 10 (call request) in the firstcommunication space 2, wherein the CONTINUE-command could be seen as thesecond event 12). After hanging up the phone 55, the core network 2′informs the operator unit 4 via the mediator unit 3 in fourteenth andfifteenth steps 56, 57 that the telephone link 54 is terminated. Asdefined in the first event-driven state-machine 14 (cp. lines 61 to 67of SEM 14) the operator unit 4 transmits again a “CONTINUE”-command tothe mediator unit 3 (sixteenth step 58) and a “U_SCREEN9”-command with atimestamp to the internet server 5 (seventeenth step 59). Furthermore,the second event-driven state-machine 15 is informed that the telephonelink 54 is disconnected by way of an “ONHOOK”-sign (eighteenth step 60,line 67 of SEM 14)). According to line 37 of the second event-drivenstate-machine 15, the SCREEN9-sign with the timestamp is transmittedtowards the Web file “MYFILE” in an nineteenth step 61 to document theexact time of terminating the telephone link 54 between Alice and Bob.Furthermore, the current transaction list is updated (increased withone), as the present transaction is terminated (cp. line 15 of SEM 15).

FIG. 4 shows a flow chart of a method for initiating a second service 13in dependency of a first service 10 according to a fourth exemplaryembodiment of the present invention. The fourth exemplary embodiment issimilar to the third exemplary embodiment illustrated in FIG. 3. AgainAlice is calling Bob. But now Bob is the served user of interest who hastwo different phones each with its own telephone number. FIG. 4 showsthe call flow relating to Bob's communication page 5′ which isconfigured in such a manner, that in the case Bob is called, both of hisphones are being alerted in parallel.

The source code and the functionality of the setup event-drivenstate-machine 16 of Bob are substantially similar to the setupevent-driven state-machine 16 of Alice, as mentioned above. The sourcecode of the setup event-driven state-machine 16 of Bob is listed below:

    <DECLARATIONS> (1)   <SERVEDUser>+49-171-6269xxx</SERVEDUser> (2)  <CUSTOMERName>Fish, Bob</CUSTOMERName> (3)  <WEB2.TPermission>extensionl</WEB2.TPermission> (4)   <MYPICTURE> (5)  http://www.ComPg.T-Mobile.org/ComPg/+49-171-6269xxx/me.jpg”   (6)  </MYPICTURE> (7)   <EDCOUNTERPLACE> (8)   http://www.EdwardArts.de/MoneyMachine” (9)   </EDCOUNTERPLACE> (10)  MYPRIVATEScheme> (11)    <Contact name=“THEFlatfish”> (12)    <PUBLIC>+49-160-1212xxx</PUBLIC> (13)     <PRIVATE>100</PRIVATE>(14)    </Contact> (15)    <Contact name=“BOBYbrown”> (16)    <PUBLIC>+49-171-6269xxx</PUBLIC> (17)     <PRIVATE>200</PRIVATE>(18)    </Contact> (19)    <Contact name=“Ed”> (20)    <PUBLIC>+49-228-936-33xxx</PUBLIC> (21)     <PRIVATE>999</PRIVATE>(22)    </Contact> (23)   </MYPRIVATEScheme> (24) </DECLARATIONS> (25)

Also, the second event-driven state-machine 15 of Bob is similar to thesecond event-driven state-machine 15 of Alice, as mentioned above.Merely, the sections <U_SCREEN2>, <U_SCREEN456>, <U_SCREEN7> and<U_SCREEN9> are not realized in Bob's second event-driven state-machine15. The source code of the second event-driven state-machine 15 of Bobis listed below:

   <ComPg Web> (1) <WEBEvents> (2)  <TELEPHONE> (3)   <ACTIONList> (4)   <ACTION>query CURRENTTransactions of SERVEDUser (5)    </ACTION> (6)   <ACTION> (7)    assign a new TRANSACTIONumber (8)    and updateCURRENTTransactions (9)    </ACTION> (10)    <ACTION> (11)     sendPUSHComPg incl. CURRENTTransactions (12)     </ACTION> (13)   </ACTIONList> (14)   </TELEPHONE> (15)   <ONHOOK> (16)   <ACTIONList> (17)      <ACTION>update CURRENTTransactions</ACTION>(18)    </ACTIONList> (20)   </ONHOOK> (21)   <U COUNTER> (22)   <ACTIONList> (23)      <ACTION>send BOBCOUNTER towards     EDCOUNTERPLACE (24)      </ACTION> (25)    </ACTIONList> (26)   </UCOUNTER> (27)  </WEBEvents> (28) </ComPg Web> (29)

Also, the first event-driven state-machine 14 of Bob is similar to thefirst event-driven state-machine 14 of Alice, wherein Bob's firstevent-driven state-machine 14 comprises a further section “STC” in his<USERACTIONList> (lines 23 to 20 of SEM 14). The section STC definesboth a DESTNumber (as known from Alice's SEM 14) for calling his firstphone and an additional DESTNumber2 for his second phone (cp lines 24,25 of SEM 14). The source code of the first event-driven state-machine14 of Bob is listed below:

   <ComPg Tel> (1) <TELEvents> (2)  <PUSHComPg> (3)   <ACTIONList> (4)   <ACTION> (5)    extend SEM according ComPg_Tel received and store (6)   CURRENTTransactions (7)  </ACTION> (8)  <USERACTIONList> (9)   CASE(CURRENTTransaction.LAST) (10)   OF SOC: (11)    <ACTION> (12)   calculate DESTNumber by mapping a (13)    called PRIVATE to PUBLICnumber (14)    </ACTION> (15)    <ACTION> (16)    for calls to Alice setCLIPNumber to my PRIVATE one (17)    </ACTION> (18)    <ACTION> (19)   arm progress types FAILURE and RELEASED (20)    </ACTION> (21)   <ACTION>send CONTINUE</ACTION> (22)   OF STC: (23)    <ACTION>setDESTNumber to my PUBLIC one</ACTION> (24)    <ACTION>set DESTNumber2 to+49-171-2146xxx</ACTION>    (25)    <ACTION> (26)    arm progress typesFAILURE and RELEASED (27)    </ACTION> (28)     <ACTION>sendCONTINUE</ACTION> (29)    <ACTION>set ACTIVELegs=2</ACTION> (30)   OFELSE: (31)     <ACTION> (32)     arm progress types FAILURE and RELEASED(33)     </ACTION> (34)      <ACTION>send CONTINUE</ACTION> (35)   CASEEND (36)  </USERACTIONList> (37) </ACTIONList> (38) </PUSHComPg> (39)<INITIAL> (40)  <ACTIONList> (42)   <ACTION> (43)   send TELEPHONE withall parameters received (44)   </ACTION> (45)  </ACTIONList> (46)</INITIAL> (47) <REPORT> (48)  <ACTIONList> (49)   CASE (PROGRESSTYPE)(50)   OF FAILURE: (51)    IF (ACTIVELegs=2) (52)    THEN (53)    <ACTION>send CONTINUE</ACTION> (54)    <ACTION>ACTIVELegs=1</ACTION> (55)    ELSE (56)     <ACTION>sendCONTINUE</ACTION> (57)     <ACTION>send ONHOOK</ACTION> (58)    FI (59)  OF RELEASED: (60)    <USERACTIONList> (61)     <ACTION>sendCONTINUE</ACTION> (62)     <ACTION>send UCOUNTER</ACTION> (63)   </USERACTIONList> (64)    <ACTION>send ONHOOK</ACTION> (65)   OFELSE: (66)    <ACTION>send CONTINUE</ACTION> (67)   CASE END (68) </ACTIONList> (69) </REPORT> (70)  </TELEvents> (71) </ComPg Tel> (72)</ComPg (73)

The call flow illustrated in FIG. 4 is similar to the call flowaccording to the third exemplary embodiment of the present inventionwhich is described in FIG. 3. The communication between the operatorunit 4 and the internet server 5, as well as between the internet server5 and the Web 6 are similar. However, the fifth step 44 comprises notonly one destination number, but two destination numbers for each ofBob's phones (“DESTNumber” and “DESTNumber2”). This leads to moretraffic between the mediator unit 3 and the core network 2′ as the corenetwork 2′ has to request two telephone links 54 between Alice and Bobin parallel, instead of a single telephone link 54 as described above.

FIG. 5 shows a flow chart of a method for initiating a second service 13in dependency of a first service 10 according to a fifth exemplaryembodiment of the present invention, wherein the fifth exemplaryembodiment is similar to the third exemplary embodiment illustrated inFIG. 3. In the fifth exemplary embodiment a call from Ed to Doris(public telephone number +49-222-32978xxx) is shown, whereby the costsfor this call are allocated to Bob's account. In order to achieve this,the first and the second event-driven state-machines 14, 15 of Bob aremodified relative to the fourth exemplary embodiment. Only the sourcecode of the setup event-driven state-machine 16 of Bob is similar to thesetup event-driven state-machine 16 of Bob, as disclosed above. Thesource code of the setup event-driven state-machine 16 of Bob is listedbelow:

    <DECLARATIONS> (1)   <SERVEDUser>+49-171-6269xxx</SERVEDUser> (2)  <CUSTOMERName>Fish, Bob</CUSTOMERName> (3)  <WEB2.TPermission>extensionl</WEB2.TPermission> (4)   <MYPICTURE> (5)  http://www.ComPg.T-Mobile.org/ComPg/+49-171-6269xxx/me.jpg”   (6)  </MYPICTURE> (7)   <EDCOUNTERPLACE> (8)   http://www.EdwardArts.de/MoneyMachine” (9)   </EDCOUNTERPLACE> (10)  MYPRIVATEScheme> (11)    <Contact name=“THEFlatfish”> (12)    <PUBLIC>+49-160-1212xxx</PUBLIC> (13)     <PRIVATE>100</PRIVATE>(14)    </Contact> (15)    <Contact name=“BOBYbrown”> (16)    <PUBLIC>+49-171-6269xxx</PUBLIC> (17)     <PRIVATE>200</PRIVATE>(18)    </Contact> (19)    <Contact name=“Ed”> (20)    <PUBLIC>+49-228-936-33xxx</PUBLIC> (21)     <PRIVATE>999</PRIVATE>(22)    </Contact> (23)   </MYPRIVATEScheme> (24) </DECLARATIONS> (25)

In contrast to the second event-driven state-machine 15 of Bob,described in the fourth exemplary embodiment of the present invention,the second event-driven state-machine 15 of Bob, as listed below,comprises an additional section called <5SINGLES+> (cp. lines 27 to 40of SEM 15). Thus, the second event-driven state-machine 15 can betriggered by a Web event <5SINGLES+> from the World Wide Web 6 (cp. line27 of SEM 15) to push the first event-driven state-machine 14 to theoperator unit 4 (cp. line 37 of SEM 15). This first web event 11 isinitialized by a further communication page 5′ of Ed, for instance(preferably triggered by a first service 10 in the World Wide Web 6).The source code of the modified second event-driven state-machine 15 ofBob is listed below:

   <ComPg_Web> (1) <WEBEvents> (2)  <TELEPHONE> (3)   <ACTIONList> (4)   <ACTION>query CURRENTTransactions of    SERVEDUser</ACTION> (5)  <ACTION> (6)   assign a new TRANSACTIONumber and (7)   updateCURRENTTransactions (8)   </ACTION> (9)   <ACTION> (10)   send PUSHComPgincl. CURRENTTransactions (11)   </ACTION> (12)  </ACTIONList> (13)</TELEPHONE> (14) <ONHOOK> (15)  <ACTIONList> (16)   <ACTION>updateCURRENTTransactions</ACTION> (17)  </ACTIONList> (18) </ONHOOK> (19) <UCOUNTER> (20)  <ACTIONList> (21)    <ACTION> (22)    send BOBCOUNTERtowards EDCOUNTERPLACE (23)    </ACTION> (24)  </ACTIONList> (25) </UCOUNTER> (26) <5SINGLES+> (27)  <ACTIONList> (28)    <ACTION> (29)   query CURRENTTransactions of SERVEDUser (30)    </ACTION> (31)   <ACTION> (32)    assign a new TRANSACTIONNumber and update (33)   CURRENTTransactions (34)    </ACTION> (35)    <ACTION> (36)     sendPUSHComPg icl. CURRENTTransactions (37)     </ACTION> (38)   </ACTIONLIST> (39)   </5SINGLES+> (40) </WEBEvents> (41)

The first event-driven state-machine 14 of Bob, as mentioned below,comprises three additional sections compared to the first event-drivenstate-machine 14 as described in connection with the fourth exemplaryembodiment of the present invention. The first additional sectionfeatures the case “WIC” in the <USERACTIONList> of the section<PUSHComPg> (cp. lines 31 to 40 of SEM 14). The case “WIC” includes thecommand “set PARTYToCall to +49-228-936-33xxx” (public number of Ed) inorder to use Ed's telephone extension as the calling party in Bob'saccount (cp. line 34 of SEM 14). Subsequently, the new variable“DORISIsCalled” is set “true” (cp. line 40 of SEM 14). Furthermore thepresent first event-driven state-machine 14 comprises the IF-cases:U_DORISIsCalled=true in the reporting sections <SUCCESS> and <RELEASED>(cp. lines 66 to 80 and lines 83 to 89 of SEM 14). The variableDORISIsCalled=true causes the setup of the destination number to+49-222-32979xxx (Doris public telephone number) (cp. line 71 of SEM 14)and a telephone link 54 between Ed and Doris is connected with the usageof Bob's account (the telephone link is enabled in the above mentionedway). The source code of the first event-driven state-machine 14 of Bobis listed below:

   <ComPg_Tel> (1) <TELEvents> (2)  <PUSHComPg> (3)   <ACTIONList> (4)    <ACTION> (5)     extend SEM according ComPg_Tel received and store(6)     CURRENTTransactions (7)     </ACTION> (8)   <USERACTIONList> (9)    CASE (CURRENTTransaction.LAST) (10)  OF SOC: (11)    <ACTION> (12)   calculate DESTNumber by mapping a called PRIVATE to    PUBLIC (13)   number (14)    </ACTION> (15)    <ACTION> (16)    for calls to Aliceset CLIPNumber to my PRIVATE one (17)    </ACTION> (18)    <ACTION> (19)   arm progress types FAILURE and RELEASED (20)    </ACTION> (21)   <ACTION>send CONTINUE</ACTION> (22)  OF STC: (23)    <ACTION>setDESTNumber to my PUBLIC one</ACTION> (24)    <ACTION>set DESTNumber2 to+49-171-2146xxx</ACTION>    (25)    <ACTION> (26)    arm progress typesFAILURE and RELEASED (27)    </ACTION> (28)    <ACTION>sendCONTINUE</ACTION> (29)    <ACTION>set ACTIVELegs⁼2</ACTION> (30)  OFWIC: (31)    <ACTION>set SERVEDUser to my PUBLIC one</ACTION> (32)   <ACTION> (33)    set PARTYToCall to +49-228-936-33xxx (34)   </ACTION> (35)    <ACTION> (36)    arm progress types FAILURE,SUCCESS and RELEASE (37)    </ACTION> (38)    <ACTION>sendINITIATE</ACTION> (39)    <ACTION>set U_DORISIsCalled=true</ACTION> (40) OF ELSE: (41)    <ACTION> (42)    arm progress types FAILURE andRELEASED (43)    </ACTION> (44)    <ACTION>send CONTINUE</ACTION> (45)  CASE END (46)  </USERACTIONList> (47)  </ACTIONList> (48) </PUSHComPg>(49) <INITIAL> (50)  <ACTIONList> (51)    <ACTION> (52)    sendTELEPHONE with all parameters received (53)    </ACTION> (54) </ACTIONList> (55)    CASE (PROGRESSTYPE) (56)    OF FAILURE: (57)    IF (ACTIVELegs=2) (58)     THEN (59)      <ACTION>sendCONTINUE</ACTION> (60)      <ACTION>ACTIVELegs⁼1</ACTION> (61)     ELSE(62)      <ACTION>send CONTINUE</ACTION> (63)      <ACTION>sendONHOOK</ACTION> (64)     FI (65)    OF SUCCESS: (66)    <USERACTIONList> (67)      IF (U_DORISIsCALLED=true) (68)      THEN(69)       <ACTION> (70)       set DESTNumber to +49-222-32978xxx (71)      </ACTION> (72)         ACTION> (73)         arm progress typesFAILURE and RELEASED (74)         </ACTION> (75)         <ACTION>sendCONTINUE</ACTION> (76)        ELSE (77)         <ACTION>sendCONTINUE</ACTION> (78)        FI (79)       </USERACTIONList> (80)     OF RELEASED: (81)       <USERACTIONList> (82)        IF(U_DORISIsCALLED=true) (83)        THEN (84)        <ACTION>sendCONTINUE</ACTION> (85)        ELSE (86)        <ACTION>sendCONTINUE</ACTION> (87)        <ACTION>send U_COUTNER</ACTION> (88)       FI (89)       </USERACTIONList> (90)       <ACTION>sendONHOOK</ACTION> (91)      OF ELSE: (92)       <ACTION>sendCONTINUE</ACTION> (93)      CASE END (94)     </ACTIONList> (95)   </REPORT> (96)   </TELEvents> (97)  </ComPg Tel> (98) </ComPg> (99)

The call flow illustrated in FIG. 5 is similar to the call flowaccording to the third exemplary embodiment of the present inventionwhich is described in FIG. 3. In contrast, the initial event in thepresent flow chart comes from the World Wide Web 6. Ed initiates Bob'scommunication page 5′ on the internet server 5 in a first step 70 byusing the command <5SINGLES+>. This command causes the secondevent-driven state-machine 15 of Bob to push the first event-drivenstate-machine 14 to the operator unit 4 in a second step 71 (cp. line 37of SEM 14). Subsequently, the section <PUSHComPg> of the firstevent-driven state-machine 14 (now included into the first application4′) is executed on the operator unit 4 in a third step 72, wherein theuser Bob is applied (as the served user) with his public number+49-717-6269xxx to the core network 2′ (cp. line 32 of SEM 14) and Ed'stelephone number +49-228-936-33xx is defined as the calling party in thecore network 2′ (cp. line 34 of SEM 14). Afterwards the core network 2′calls Ed's telephone extension as the calling party address in fourthsteps 73. In a fifth step 74 the core networks 2′ informs the firstevent-driven state-machine 14 that the routing of Ed's telephoneextension has been successful by using the command REPORT(SUCCESS).Consequently, the first event-driven state-machine 14 is triggered (cp.lines 66 of SEM 14) and the destination number is set to Doris publicnumber +49-222-32978xxx (cp. line 71 of SEM 14) which is sent to thecore network 2′ in a sixth step 75 (cp. line 76 of SEM 14). The corenetwork 2′ calls Doris public number and enables a telephone link 54between Ed and Doris in seventh steps 76. After the telephone link 54 isterminated 55 (by hanging up the phone, for instance) the core network2′ sends the command REPORT(RELEASED) to the operator unit 4 in a eighthstep 77. This command triggers again the first event-drivenstate-machine 14 (cp. line 81 of SEM 14) and subsequently theevent-driven state-machine 14 answers with the event “CONTINUE” in aninth step 78 (cp. 85 of SEM 14). Furthermore, the first event-drivenstate-machine 14 sends the “ONHOOK”-signal to the second event-drivenstate-machine 15 on the internet server 6 in a tenth step 79 (cp. line91 of SEM 14).

The invention claimed is:
 1. A method for initiating a second service independency of a first service using individually configured event-drivenstate-machines, the method comprising: executing the first service in afirst communication space; transmitting a first event to an operatorunit in dependency of the first service; triggering a first event-drivenstate-machine of the operator unit by the first event; generating asecond event by the first event-driven state-machine; transmitting thesecond event to at least one of the first communication space and asecond communication space; and initiating the second service in the atleast one of the first communication space and the second communicationspace by the second event; wherein the first event-driven state-machineis pushed from an internet server to the operator unit by a secondevent-driven state-machine; wherein the first event-driven state-machineis individually configurable by a user for initiating the second eventin dependency of the first event; wherein: an initial first servicetriggers an initial web event which is transmitted to the secondevent-driven state-machine by a first application of the operator unit,wherein the initial web event triggers the second event-drivenstate-machine in such a manner that the first event-driven state-machineis pushed to the operator unit; and the first event-driven state-machineis initially pushed from the internet server towards the operator unitby the second event-driven state-machine in such a manner that the firstapplication includes at least partially the functionality of the firstevent-driven state-machine.
 2. The method according to claim 1, whereinthe second event-driven state-machine is individually configurable bythe user for pushing the first event-driven state-machine to theoperator unit.
 3. The method according to claim 1, wherein the firstevent-driven state-machine is initially pushed from the Internet servertowards the operator unit by the second event-driven state-machine insuch a manner that the first application includes the source-code of thefirst event-driven state-machine.
 4. The method according to claim 1,wherein a first communication between the first communication space andthe operator unit is controlled by the first event-driven state-machinewhich is pushed towards the operator unit, and wherein a secondcommunication between the internet server and the internet is controlledby the second event-driven state-machine on the internet server.
 5. Themethod according to claim 1, wherein the first communication space islinked to the operator unit via a mediator unit, and wherein themediator unit transforms a data type of the first communication spaceinto a data type applicable for the first event-driven state-machine andtransforms a data type of the first event-driven state-machine into adata type applicable for the first communication space.
 6. The methodaccording to claim 1, wherein the second communication space is linkedto the internet server via a further operator unit comprising a furtherfirst event-driven state-machine.
 7. The method according to claim 6,wherein the further event-driven state-machine is pushed to the furtheroperator unit by the second event-driven state-machine.
 8. The methodaccording to claim 1, wherein the internet server comprises a setupevent-driven state-machine representing at least one of an individuallyconfigured setup of the user and personal information about the user. 9.The method according to claim 1, wherein at least one of the first, thesecond, the further first and the setup event-driven state-machines areprovided by a web page on the internet server featuring a well-definedUniform Resource Identifier, wherein a web page is allocated to at leastone of a first user and a first group of users and wherein the at leastone of the first user and the first group of users is allocated awell-defined ID in the corresponding communication space.
 10. The methodaccording to claim 1, wherein at least one of the first, the second, thefurther first and the setup event-driven state-machines are configuredby at least one of uploading an algorithm to the internet server, onlinemodification of the algorithm on the internet server and clearing thealgorithm by a provider.
 11. The method according to claim 10, whereinthe at least one of the first, the second, the further first and thesetup event-driven state-machine is configured by the user with the aidof a graphical user interface, wherein the graphical user interfacecomprises at least one of templates and a compiler which transformsgraphical inputs from the user into an applicable computer language fora corresponding event-driven state machine.
 12. The method according toclaim 1, wherein at least one of the first and the second communicationspace comprise at least one of a telephone network, a mobilecommunications network, the internet, an intranet, a next generationnetwork, a wireless local area network, domains, subdomains, electricalsystems of communication devices, electronic systems of communicationdevices, global positioning devices, building services, portablepersonal devices, alarms systems, phones, mobile phones, presentationtools, and electrical consumer products.
 13. The method according toclaim 1, wherein the method is used as a user-configurable communicationinterface between at least two different first and second communicationspaces.
 14. A tangible, non-transitory computer-readable medium, part ofan internet server, comprising: a first event-driven state-machine; asecond event-driven state-machine; and computer-executable instructionsfor initiating a second service in dependency of a first service usingthe event-driven state-machines, the computer-executable instructionscomprising: instructions for pushing, by the second event-drivenstate-machine, the first event-driven state-machine at least partiallyfrom the internet server to an operator unit, when the secondevent-driven state-machine detects an initial event from a firstcommunication space, wherein the first event-driven state-machinecontrols a first communication between the operator unit and the firstcommunication space; wherein: an initial first service triggers aninitial web event which is transmitted to the second event-drivenstate-machine by a first application of the operator unit, wherein theinitial web event triggers the second event-driven state-machine in sucha manner that the first event-driven state-machine is pushed to theoperator unit; and the first event-driven state-machine is initiallypushed from the internet server towards the operator unit by the secondevent-driven state-machine in such a manner that the first applicationincludes at least partially the functionality of the first event-drivenstate-machine.
 15. An operator unit, comprising a processor and atangible, non-transitory processor-readable medium havingprocessor-executable instructions stored thereon for initiating a secondservice in dependency of a first service using individually configuredevent-driven state-machines, wherein the processor, based on executionof the processor-executable instructions, is configured for: executingthe first service in a first communication space; transmitting a firstevent to an operator unit in dependency of the first service; triggeringa first event-driven state-machine of the operator unit by the firstevent; generating a second event by the first event-drivenstate-machine; transmitting the second event to at least one of thefirst communication space and a second communication space; andinitiating the second service in the at least one of the firstcommunication space and the second communication space by the secondevent; wherein the first event-driven state-machine is pushed from aninternet server to the operator unit by a second event-drivenstate-machine; wherein the first event-driven state-machine isindividually configurable by a user for initiating the second event independency of the first event; wherein: an initial first servicetriggers an initial web event which is transmitted to the secondevent-driven state-machine by a first application of the operator unit,wherein the initial web event triggers the second event-drivenstate-machine in such a manner that the first event-driven state-machineis pushed to the operator unit; and the first event-driven state-machineis initially pushed from the internet server towards the operator unitby the second event-driven state-machine in such a manner that the firstapplication includes at least partially the functionality of the firstevent-driven state-machine.
 16. The operator unit according to claim 15,wherein the operator unit is further configured to allow the firstevent-driven state-machine to be pushed from the internet server to theoperator unit by a second event-driven state-machine; wherein theoperator unit further comprises the first application, which isconfigured to include at least partially a functionality of the firstevent-driven state-machine; wherein at least the first event-drivenstate-machine is individually configurable by a user for initiating thesecond event in dependency of the first event in such a manner that thefirst application of the operator unit includes at least partially thefunctionality of the first event-driven state-machine.
 17. The operatorunit according to claim 16, wherein the first application is furtherconfigured to include at least partially a source code of the firstevent-driven state machine.